Caching html fragments

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject: Caching html fragments

Feedback Type: Question

Product Area: Domino Server

Technical Area: Application Development

Platform: ALL

Release: 8.5

Reproducible: Not applicable

I have a web application which serves mostly static pages. I have incorporated some semi-dynamic content into these static pages by performing a looking on a set of "cache" documents.

Ex: A web page contains a list of news items. A cache document containing the HTML for the news list is rebuilt in a scheduled agent which runs every 30 minutes. The static page has a computed text which performs a dblookup to retrieve the html from the cache and display it on the mostly static page.

Using this method, most of the work is done in the scheduled agent, so the page still loads relatively quickly.

The problem is, the caches are limited to 32K characters. If the cache needs to be larger than that, then it has to be stored in a rich text field, which cannot be retrieved by a dblookup.

I'm trying to find a way around this, which preserves the performance gain and isn't too cumbersome to use. Has anyone done this sort of thing before?

The ideas that I have considered are:

Storing the cache in a rich text field, and having a WQO agent retrieve it and copy it into a local RT field, then having the computed text just do a @Text(LocalRTField). This won't work on PAGES, and would be more cumbersome, since I would need a field to control which caches to load, and what fields they were stored in. Also it would require the performance overhead of running a WQO agent (not sure how significant this is).

Having client side javascript load the contents of a web-visible cache after the initial load of the page. This obviously would reduce the server work, but would require at least two round trips for the client to load everything. Also, browsers without javascript will not load the cached content.

Feedback number WEBB97VN2R created by ~Carol Asafreekonyli on 05/20/2013

Status: Open
Comments: